@UsamaSadiq given how late the release has been and how at this point, we will not have run a sandbox that tests this for all the test cases that BTR runs, I think it makes more sense to not try to backport this and be okay with just waiting till Verawood for this. We can still start dropping support for 3.11 in the mean time on master but I'm worried to introduce anything else that might introduce unfroseen issues or delays in the release of Ulmo.

@UsamaSadiq given how late the release has been and how at this point, we will not have run a sandbox that tests this for all the test cases that BTR runs, I think it makes more sense to not try to backport this and be okay with just waiting till Verawood for this. We can still start dropping support for 3.11 in the mean time on master but I'm worried to introduce anything else that might introduce unfroseen issues or delays in the release of Ulmo.

Yes, this seems more reasonable. Before dropping support for Python 3.11, we'll need to confirm the status of sandbox service too as that will be a blocker for platform Python 3.12 upgrade.

Closing since we decided not to backport this.